Stakeholder Requirements Definition

Purpose

The Stakeholder Requirements Definition process translates stakeholder capability needs into a set of technical requirements. The process helps ensure each individual stakeholder’s requirements, expectations and perceived constraints are understood from the acquisition perspective.

drawing showing green circles with white exclamation points labeled capability needs going through funnel labeled stakeholder requirements definition and ending up in checklist labeled technical requirements

Failing to perform an exhaustive Stakeholder Requirements Definition process could result in significant requirements creep, rework due to misunderstanding of end-user needs, unexpected contract modifications, cost growth and schedule slip. The objective of this process is to help ensure that stakeholder requirements are feasible, balanced and fully integrated as more information is learned through requirements analysis.

Stakeholder Requirements Definition bridges the gap between the identification of a materiel need, described in the Joint Capabilities Integration and Development System (JCIDS) CJCSI 5123.01, and the acquisition of a materiel solution, governed by the Defense Acquisition System, i.e., DoDD 5000.01 and DoDI 5000.02.

Relationship to Requirements Analysis and Architecture Design

The Stakeholder Requirements Definition process complements Requirements Analysis and Architecture Design (see SE Guidebook Section 4.2.2 Requirements Analysis Process and SE Guidebook Section 4.2.3 Architecture Design Process, respectively).

pie chart divided into thirds with words stakeholder requirements definition, requirements analysis, and architecture design

These three processes are recursively applied at each level of the system’s specifications and then iteratively within each level throughout development.

mockup of example system specification with three levels. Pie chart applied to each of the three levels.

Role of the Program Manager and Systems Engineer

The Program Manager (PM) and Systems Engineer are responsible for supporting the Stakeholder Requirements Definition process and should work with the end user to establish and refine operational needs, attributes, performance parameters and constraints documented in JCIDS documents.

Stakeholder Requirements Definition activities are performed throughout the acquisition life cycle and include the following activities:

  • Elicit stakeholder capability objectives
    • Identify stakeholders who have an interest in the system and maintain relationships with the stakeholders and their organizations throughout the system’s entire life cycle.
    • Elicit capability objectives from the stakeholders about what the system will accomplish and how well.
  • Define stakeholder requirements
    • Define the perceived constraints on a system solution.
    • Define the relevant environment (including threat target and critical intelligence parameters per JCIDS Manual Page B-28) and support scenarios that can be used to analyze the operation of the system.
    • Define potential requirements that may not have been formally specified by any of the stakeholders.
  • Analyze and maintain stakeholder requirements
    • Analyze requirements for specificity, completeness, consistency, measurability, testability and feasibility.
    • Negotiate modifications with stakeholders to resolve requirement discrepancies.
    • Validate, record and maintain stakeholder requirements throughout the system life cycle.
    • Support the Requirements Analysis process to establish and maintain a traceability matrix to document how the system requirements are intended to meet the stakeholder objectives and achieve stakeholder agreements.

Requirements Source

The authoritative source for stakeholder requirements are documents produced via the JCIDS such as the Initial Capabilities Document (ICD) and Capability Development Document (CDD). JCIDS analyzes gaps in existing and/or future warfighting operations and provides a process that allows the Joint Requirements Oversight Council to balance joint equities and make informed decisions on validation and prioritization of capability needs. (Also, see DoD SE Guidebook, Section 4.2.1.).

Products and Tasks

Product Tasks
AWQI 2-1-1: Document of baseline technical requirements
  1. Identify stakeholders who have an interest in the system.
  2. Elicit stakeholder capability objectives.
  3. Define stakeholder requirements.
  4. Given an initial capabilities document (ICD), define potential requirements that are not formally specified (i.e., derived requirements).
  5. Document defined stakeholder requirements and derived technical requirements.
  6. Inform the requirements analysis process to establish, maintain, and capture traceability between system requirements and stakeholder requirements.

Source: AWQI eWorkbook

Resources

Key Terms

Policy and Guidance

  • SE Guidebook Section 4.2.1 Stakeholder Requirements Definition Process
  • Joint Capabilities Integration and Development System (JCIDS) Manual, 2021, Enclosure B – Appendix G, Development of Performance Attributes
    • JCIDS Manual, 2021, Enclosure B – Appendix G – Annex A, Interoperability Guide
    • JCIDS Manual, 2021, Enclosure B – Appendix G – Annex B, Force Protection KPP Guide
    • JCIDS Manual, 2021, Enclosure B – Appendix G – Annex C, System Survivability KPP Guide
    • JCIDS Manual, 2021, Enclosure B – Appendix G – Annex D, Sustainment KPP Guide
    • JCIDS Manual, 2021, Enclosure B – Appendix G – Annex E, Energy KPP Guide
    • JCIDS Manual, 2021, Enclosure B – Appendix G – Annex F, DOTmLPF-P Guide
  • Engineering Guidebook, OUSD(R&E)/DD Engineering, 2022
  • SEBoK - Stakeholder Needs Definition
  • SEBoK - Stakeholder Requirements Definition
  • IEEE 15288.1-2014 Section 6.4.2 Stakeholder Needs and Requirements Definition Process
  • MIL-STD-961 Defense and Program-Unique Specifications Format and Content
  • SD-15 Guide for Performance Specifications
  • Systems Engineering Plan (SEP)Outline Section 2.1 Requirements Development

DAU Training Courses

  • ENG 1110 Stakeholder Requirements
  • CLE 074 Cybersecurity Throughout DoD Acquisition
  • ENG 1110 Stakeholder Requirements
  • ETM 1030, Requirements Definition and Analysis Fundamentals, Lesson 3: Refining Operational Needs
  • RQM 1010 Introduction to the Joint Capabilities Integration & Development System
  • RQM 1101 Core Concepts for Requirements Management
  • RQM 2520Developing Performance Attributes
  • RQM 110, Core Concepts for Requirements Management
  • RQM 2100, Application Skills for Requirements Managers
  • SWE 0016 Capability Needs Statement
  • WSM 007 Stakeholder Management
  • WSM 008 Developing Performance Requirements for Service Acquisitions
  • WSM 009 Work Statement Workshop (SOW, SOO, PWS)
  • WSM 010 Statement of Work Workshop
  • WSS 001 Cybersecurity and Acquisition Integration
  • WSS 013 Cyber Training Range – Aviation Systems

DAU Media

DAU Communities of Practice

On this page

  1. Purpose
  2. Relationship to Requirements Analysis and Architecture Design
  3. Role of the PM and SE
  4. Requirements Source
  5. Resources
Back to top